Checking the system configuration

For large installations (cluster, data distribution or client system), it is important that the services run with the correct configuration.

In an installation with data distribution (see Data Distribution Over Several Installations), for example, it would be possible for a subordinate installation to have not yet received the configuration of the main installation (this can also occur after a computer restart in special cases).

The configuration can be viewed and also reloaded via the system area.

To open the web administration, enter http://<hostname>/webadmin in the web browser (where hostname corresponds to the server on which IQ4docs WebAdmin was installed). In a client environment, enter the URL that you received from the client administrator (for example, http://server/webadmin/#/cf992178-4bd6-431c-b815-b9d734d0ded3). If you are not already logged in, log in with a user that has administrator rights (login and password) or as the IQ4docs system administrator (administrator with password admin by default).

In the Web administration, click System > System Areas in the menu. The list view of the system areas opens. The Standard Area system area is present by default.

Open the desired area via the Edit icon at the end of the line or the Edit System Area button below the table.

Then, in the details dialog of the system area, in the Server (Cluster Nodes) section, click ... at the end of the line and then click Query Service Versions.

Clicking on ... at the end of the line of a server (cluster node) and then on Query Service Versions opens a window in which all services are listed.

You can query the versions of all services of the server here – this also happens automatically when you open the list. This also checks whether the services are available.

Services that were queried correctly are marked with a green check mark and show the version number. If services cannot be queried, a yellow warning symbol appears along with Service Unavailable or Not Found.

The following information is available for each service:

Field Description
Service name Designation of the service.
Version Version number of the service with build commit (this allows developers to accurately identify the version).
MongoDB hostname Name of the MongoDB server (cluster node) to which the service is connected. This can also be more than one if a comma separated list is entered in the LocalService.config of the service.
RabbitMQ hostname Name of the RabbitMQ server (cluster node) to which the service is connected. This can also be more than one if a comma separated list is entered in the LocalService.config of the service.
Area System area of the service

For this purpose, all technical configuration data for each service can be displayed using the > at the beginning of the line. This is the actual data in JSON format that the service uses.

If the MongoDB, RabbitMQ or System Area data in the list are not filled in, the version of the service is not (yet) able to provide this information.

At the end of the line, click ... and in the menu that opens, click Reload Configuration. This causes the configuration to be requested again by the service, i.e. the configuration with which the service is currently running is loaded again.

At the end of the line, click ... and in the menu that opens, click Reload Version. This will reload the version from the service and display it in the Version column.

At the end of the line, click ... and in the menu that opens, click Reconfigure Service to reconfigure a single service. The service then requests its configuration data from ConfigService again and uses it.

To reconfigure all services at once, use the Reconfigure All Services button below the list.